fep: propose sig-os and sig-riscv as planned SIGs#35
Conversation
fb037b8 to
bdef86b
Compare
wbavon
left a comment
There was a problem hiding this comment.
Per the 72-hour lazy consensus rule, this PR has received no objections since submission (June 10). The planned SIG charters and table entries look good and can be merged.
Two reminders:
-
FEP directories —
fep/sig-os/andfep/sig-riscv/are included in this PR. Under the transitional rules, FEPs without an active SIG home go underfep/sig-architecture/. These directories are fine as placeholders, but they do not make these SIGs active. -
Chair appointment — A SIG without a Chair is not a formal SIG. It cannot hold its own meetings, approve FEPs, or exercise decision-making authority. Until a Chair is confirmed, relevant FEPs and modules remain under TSC review. Please identify Chair candidates for both SIGs as soon as possible so they can move from Planned to Active status.
Summary
Proposes two new Planned SIGs following the community governance structure (
GOVERNANCE.md,sigs/README.md):sig-os— OS-level packaging (.deb/.rpm/wheel), FlagOS Nexus publishing, distribution integration (openKylin, openEuler). Charter:sigs/_planned/sig-os.md. Needed by FEP-19 (fep: unified package integration for FlagOS repositories #19).sig-riscv— experimental RISC-V support:riscv64compile adaptation + dependency analysis. Charter:sigs/_planned/sig-riscv.md. Needed by FEP-34 (fep(sig-riscv): add experimental support FEP #34).Neither area has a Chair candidate or standing member roster yet, so both are proposed as Planned rather than Active — matching sig-edge / sig-tools / sig-architecture. Until activation, their FEPs are reviewed directly by the TSC per the bootstrap note in
fep/README.md.What this PR does
sigs/_planned/sig-os.mdandsigs/_planned/sig-riscv.md(charter drafts in the established format: Reason for Deferred Activation / Planned Responsibilities / Current Interim Arrangement).sigs/README.mdwith activation criteria.fep/README.mdandfep/README_CN.md.fep/sig-os/andfep/sig-riscv/FEP home directories (.gitkeep), consistent with existing planned SIGsig-architecture.History
This PR originally registered the SIGs under the pre-restructure convention (
fep/sig-*/OWNERS+ rows in the old SIG table). After the governance restructure landed onmain, it was rebuilt from scratch on the new structure (force-pushed).Follow-ups
fep(sig-os): unified package integration, FEP-19) — TSC-reviewed until sig-os activates.fep(sig-riscv): experimental support, FEP-34) — TSC-reviewed until sig-riscv activates.